Columbia Kermit/kermit.zip/newsgroups/misc.19970626-19970929/000340_news@newsmaster….columbia.edu _Thu Sep 11 04:58:32 1997.msg

Internet Message Format | 2020-01-01 | 9KB

Return-Path: <[e-mail]>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
    by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id EAA13551
    for <[e-mail]>; Thu, 11 Sep 1997 04:58:22 -0400 (EDT)
Received: (from news@localhost)
    by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id EAA12359
    for kermit.misc@watsun; Thu, 11 Sep 1997 04:58:21 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!newsfeed.internetmci.com!newsfeed.internetmci.com!205.185.79.5!zdc!szdc!newsp.zippo.com!mdrn
From: [e-mail]
Newsgroups: comp.protocols.kermit.misc
Subject: RE: MSDOS Kermit to Kermit/2..
Date: 11 Sep 1997 00:41:11 -0700
Organization: None
Lines: 201
Message-ID: <[e-mail]>
NNTP-Posting-Host: MHS
Xref: news.columbia.edu comp.protocols.kermit.misc:7662


  >     Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
        wrote:

  > Newsgroups:  comp.protocols.kermit.misc
  > Subject:  Re: MSDOS Kermit to Kermit/2 script conversion notes
  > Date:  8 Sep 1997 13:54:19 GMT
  > Organization:  Columbia University
  > Lines:  168
  > Message-ID:  <5v102b$cen$[e-mail]>
  > References:  <[e-mail]>
  > NNTP-Posting-Host:  watsun.cc.columbia.edu
  > Xref:  news.reference.com comp.protocols.kermit.misc:609
  >
  >
  >
  > In article <[e-mail]>,
  >  <[e-mail]> wrote:
  > :
  > : [I'm cross-posting this to several forums where I think it will be
  > : appropriate for discussion.
  > : I apologize to anyone who finds it inappropriate (or long winded).]
  >
  > It is considered polite to cross-post by listing all of the newsgroups
  > in one copy of the post instead of sending separate posts to each
  > group.  That way every group gets to see the responses.

Sorry.  I posted this via [e-mail]
because I've found it more reliable about actually getting something on the
newsgroups than my supposedly direct Usenet access (and less trouble than
DejaNews)
I also posted to [e-mail] since I
viewed it as dealing with 'setup' (right or wrong).
There, the only response I got so far was some email from a service at:

http://www.experts-exchange.com




  >
  > : Some notes on converting command files from MS-DOS Kermit 3.14 to
  > : Kermit/2 (Kermit-95 (C-Kermit for Windows-95) for OS/2)
  > : (henceforth referred to as K2, K/2 or K2.EXE)
  > : I welcome any comments:
  > :
  > : 1) The OS/2 "EXTPROC" command seems to be the most underdocumented
  > :    OS/2 command I've come across.  Few of the BIG, THICK OS/2 books
  > :    (henceforth referred to as BTOB's) had much on it.  Almost nowhere
  > :    was there a real working example of it.
  > :    I expected it to be something similar to the UNIX
  > :    "#!/full/path/specification/to/the/interpreter" feature for the
  > :    first line of a script.  Almost, but not quite.
  > :    The documentation all said something to the effect of:
  > :
  > :    EXTPROC <device>:\full\path\interpreter <parameters here>
  >
  > That is the correct syntax for EXTPROC, but ...
  >
  > :    I *expected* to use something like:
  > :
  > :    EXTPROC <device>:\full\path\k2.exe = %1 %2 %3 %4 %5  %6 %7 %8 %9
  >
  > This is not the syntax for Kermit-95.  K95 (and C-Kermit) requires that
  > the command file be the first parameter on the command line.
  >
  > :  on the first line of the procs to use them as OS/2 commands that
  > : would pass the parameters to the script previously used for
  > : MS-DOS Kermit into \&@[0] ... \&@[8].
  > :
  > : What I found was needed was:
  > :
  > :    EXTPROC <device>:\full\path\k2.exe <device>:\full\path\to\the\script.c
md
  >
  > That is almost correct.
  >
  > Try just
  >
  > ^HEXTPROC K2.EXE
  >
  > assuming that K2.EXE is in your PATH.  Then it should work fine.  OS/2
  > will expand the current .CMD file and use that as the first parameter,
  > and then the .CMD command line parameters will follow it.
  >
  > You can then access the command line parameters using command line
  > argument array \&@[].
  >..............................................................

I think I was confused by the little bit of EXTPROC (in OS/2) documentation
I had access to, which coupled with the generic C-Kermit documentation
made me think that parameters *needed* to be on the script EXTPROC line,
after the interpreter is specified.
Here is what I found to work, when the .CMD file is both in the
path, or the current directory:

EXTPROC D:\K2\K2.EXE
; C:\USR\COMM\Ktest7.CMD
; LAFN login script
; DEL 30/01/97
echo \&@[0] \&@[1] \&@[2] \&@[3] \&@[4] \&@[5] \&@[6] \&@[7] \&@[8] \&@[9] \&@[
10]
IF DEFINED \&@[2] ASSIGN \%1 \&@[2]
IF DEFINED \&@[3] ASSIGN \%2 \&@[3]
IF DEFINED \&@[4] ASSIGN \%3 \&@[4]
echo \%1 \%2  \%3 \%4 \7 \7 \7 \7 \7 the input
echo Ktest7!\13\10
EXIT

then I type:
ktest7 a b c d e f g

which output:
Executing D:\K2\K2\EXE for OS/2
Good Evening, smile.
D:  KTEST7.CMD  a b c d e f g
a b c the input
Ktest7!

This is acceptable to me.
Does it seem like I'm clear on the concept?

  >
  > : 2) While functioning as a comment in K/2, and apparently in
  > : most versions of C-Kermit, EXTPROC required some bogus
  > : definition as a macro to minimize interuption when scripts
  > : were run back with MS-DOS Kermit, I think I just
  > : "define EXTPROC echo" in my MSCUSTOM.INI file to allow things
  > : to flow smoothly.
  >
  > EXTPROC is not supported in DOS.  Therefore, I do not believe that
  > anybody ever thought to add it there.

My goal is to make some command file scripts executable in several OS's on my
machine in as many ways as possible, with just one file holding the script -
various flavors of DOS and DOS Emulators, OS/2 and LINUX C-Kermit
from within the appropriate version of Kermit.
Also at least some of the command files should be able
to be executed from either the OS/2 or Linux shell command lines.
(I think both being impossible due to the mutual exclusion of EXTPROC and
#! both being on the first line, but the changes to convert from one to the
other should be pretty mechanical.  Maybe there is some trick, but I haven't
given it much thought.)

  >
  > : 4) The GUI dialer works fine for targets where dialing in
  > : .....................................................
  > The dialer provides for automatic retries.  No scripting required.
  > This is built into K95's DIAL command.  The number of retries,
  > interval between retries, etc are located on the Location->General
  > page.
  >
  > If your host has multiple phone numbers you want to try use a Dialing
  > directory and specify the dialing directory entry name in the phone
  > number field instead of an actual phone number.  K95 will auto-dial
  > through the entire list.
  >
  > The dialer will not prompt for the password.  However, you can specify
  > your own wrapper script that will prompt for the password and then
  > TAKE LOGIN.KSC to login.  I will consider adding this feature.
  >

Thanks for the consideration, and the pointers.

  > : 5) I found I was frequently having to modify portions of the
  > : .............................
  > :
  > You will have to show us the script you are using to login in for us
  > ............................................................
  >
  > Send support questions to [e-mail].
  >
  >     Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
  >                  The Kermit Project * Columbia University
  >        612 West 115th St #716 * New York, NY * 10025 * [phone]
  >     http://www.columbia.edu/kermit/k95.html * [e-mail]

  >

Before I take you up on that, let me experiment some more - this last
item wasn't really anything *failing* to work, it just didn't seem
intuitive to me.

Again, much thanks - you guys have unbelievable patience.


Regards,
Dallas E. Legan II
(562) 862 - 4854 ext. '*'
[e-mail]
[e-mail]
[e-mail]

"But I found that the rulers were ordinary men, too, and frequently
as bewildered as I was."

                from "Solution Unsatisfactory"
                   by Robert A. Heinlein

I speak only for myself, and assume full responsibility for my statements.